-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Infra UI] Update Processes tooltips #166251
[Infra UI] Update Processes tooltips #166251
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally, looks good ✨ Left a few comments for the code but they are totally non-blocking.
'https://www.elastic.co/guide/en/observability/current/view-infrastructure-metrics.html'; | ||
const SYSTEM_INTEGRATION_DOCS_LINK = 'https://docs.elastic.co/en/integrations/system'; | ||
|
||
export const TopProcessesTooltipContent = React.memo(() => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be better to name the file and component inside using the same name, but I'm not sure how strictly we follow this convention usually
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After moving the popup here I renamed it to TopProcessesTooltip
which matches the file name
|
||
export const TopProcessesTooltipContent = React.memo(() => { | ||
const onClick = (e: React.MouseEvent<HTMLDivElement, MouseEvent>) => { | ||
e.stopPropagation(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you clarify please why this is needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was added initially as a bug fix because of the table sorting issue with the tooltip there #161565 but in this case, I don't think we need it - removed 👍
@@ -119,23 +120,19 @@ export const Processes = () => { | |||
</EuiTitle> | |||
</EuiFlexItem> | |||
<EuiFlexItem grow={false}> | |||
<EuiIconTip | |||
<Popover |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if it makes sense to put the whole popover into the dedicated component instead of just its content. it would declutter a bit the parent component, and strictly speaking, there is no need to have the content separately as we don't use it anywhere else. wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes in this case it makes sense to keep the Popover
inside the other component as the content is not used anywhere else 👍 Changed
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: |
Thank you for addressing the comments 🙌 |
Closes #165822
Summary
This PR moves the explanation tooltip to the top processes title and changes the explanation text:
Testing
top_processes_popup.mov